Re: psqlodbc and SQLFetch after SQLTables gives

At 0:24 +0900 2003/02/11, Hiroshi Inoue wrote:
>  > -----Original Message-----
>  > From: Giuliano Gavazzi
[...]
>  > >  > Now I have enabled tracing and found where the failure is. Apparently
>>  >>  MSQ uses SQLFetch just after SQLTables to get the table list, this
>>  >  > SQLFetch fails by returning SQL_NO_DATA_FOUND. Here I have two
>>  >>  snippets from the traces of MSQ retrieving tables first using
>>  >>  OpenLink Postgres Lite driver (that succeeds) and then using psqlodbc
>>  >>  (that fails):
>>  >>
>>  >>  1) openlink driver:
>>  >>
>>  >>  iODBC[Microsoft Query]  ThID:A0000DEC  ENTER SQLTables
>>  >>
>>  >>  iODBC[Microsoft Query]  ThID:A0000DEC  EXIT  SQLTables  with return
>>  >>  code 0 (SQL_SUCCESS)
>>  >>
>>  >>  Microsoft Query  ThID:A0000DEC  EXIT  SQLTables  with return code 0
>>  >>  (SQL_SUCCESS)
>>  >>             HSTMT         0x01619a00
>>  >>             CHAR*         00000000 "..."
>>  >>             SMALLINT      -3536
>>  >>             CHAR*         00000000 "..."
>>  >>             SMALLINT      -18992
>>  >>             CHAR*         00000000 "..."
>>  >>             SMALLINT      15056
>>  >>             CHAR*         0x001c3fd8 "Table"
>>  >
>>  >Hmm, if it is "TABLE", it seems to work.
>>  >OK I would change the driver to be insenitive about
>  > >it.
[...]
>I've just committed a change to cvs(info.c).
>Please try it.
>
>regards,
>Hiroshi Inoue

tested...
Thanks Hiroshi, you are a star!
You can add a note in the CVS that this change fixes the interaction
with MSQuery on MacOSX.

Giuliano